specify main branch in configuration
#107
Conversation
|
This repo has been inactive for a long time and we're pondering a completely different way to benchmark over here: Can you please justify why this PR is needed? There is no description in your PR original post. Thanks! |
|
Just to clarify a bit. We started running the astropy benchmarks here at STScI and would like to post the results at the usual place (something that will be discussed at the next astropy infrastructure meeting). Zach will clarify the issue with the branch naming. I don't want to impose a solution on how to run the benchmarks. If the project decides to go a different way that's fine. We need some estimates now and the easiest and fastest way to get these estimates is to run use what we already have. |
Okay. Do you want to keep this open until after the meeting? I don't have a problem merging it now as it looks uncontroversial but I just want to make sure STScI knows Astropy's plan (or lack of). Please let know. Also, if you need invites to the meeting, please DM me. Thanks! |
|
It is my understanding that @zacharyburnett would open a separate PR to sync his fork to this repo, which would also include this patch, so closing without merge. cc @WilliamJamieson Thanks for your patience! |
running
asv gh-pagesresults in an error as it assumes the default branch is namedmaster; this is a small fix to make that work